const WEIGHTS = {
  adoption: {
    downloads: 0.75, // dominant signal because they best reflect real-world adoption (in the data we have through facets currently)
    freshness: 0.15, // small correction so stale packages are slightly 
    likes: 0.1, // might be pumped up in the future when ./npmx likes are more mainstream
  },
  efficiency: {
    installSize: 0.3, // weighted highest because it best reflects consumer footprint

    // dependency weights are already measured in install size in some way, but still useful knobs to find the sweet spot
    dependencies: 0.05, // direct deps capture architectural and supply-chain complexity
    totalDependencies: 0.2, // same for total deps

    packageSize: 0.1,
    vulnerabilities: 0.2, // penalize security burden
    types: 0.2, // TS support
    // Note: the 'deprecated' metric is not weighed because it just forces a -1 evaluation
  },
}

/* Fixed logarithmic ceilings to normalize metrics onto a stable [-1, 1] scale.
*  This avoids dataset-relative min/max normalization, which would shift scores depending
*  on which packages are being compared. Ceilings act as reference points for what is
*  considered 'high' for each metric, ensuring consistent positioning across different
*  datasets while preserving meaningful differences via log scaling. 
*/
const LOG_CEILINGS = {
  downloads: 100_000_000,
  likes: 1000, // might be pumped up in the future when ./npmx likes are more mainstream
  installSize: 25_000_000,
  dependencies: 100,
  totalDependencies: 1_000,
  packageSize: 15_000_000,
}

const VULNERABILITY_PENALTY_MULTIPLIER = 2